FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource CapabilityStatement/FHIR Server from package hl7.fhir.us.exchange-routing#current (32 ms)

Package hl7.fhir.us.exchange-routing
Type CapabilityStatement
Id Id
FHIR Version R4
Source http://hl7.org/fhir/us/exchange-routing/https://build.fhir.org/ig/HL7/fhir-exchange-routing-ig/CapabilityStatement-exchange-routing-destination-server.html
Url http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-destination-server
Version 1.0.0
Status active
Date 2022-05-17T00:00:00-05:00
Name ExchangeRoutingDestinationServerCapabilityStatement
Title Exchange Routing Destination Server Capability Statement
Experimental False
Realm us
Authority hl7
Description This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.
Kind requirements

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

ExchangeRoutingDestinationServerCapabilityStatement

This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.

ModeSERVER
Description

When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the destination server SHALL populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. When participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server SHOULD: 1. Support the XML source format.

Transaction
System History
System Search
Resource TypeProfileReadSearchUpdateCreate

Source

{
  "resourceType" : "CapabilityStatement",
  "id" : "exchange-routing-destination-server",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>ExchangeRoutingDestinationServerCapabilityStatement</h2><div><p>This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.</p>\n</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td><div><p>When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the destination server <strong>SHALL</strong> populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format.\nWhen participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server <strong>SHOULD</strong>: 1. Support the XML source format.</p>\n</div></td></tr><tr><td>Transaction</td><td></td></tr><tr><td>System History</td><td></td></tr><tr><td>System Search</td><td></td></tr></table><table><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th><b title=\"GET a resource (read interaction)\">Read</b></th><th><b title=\"GET all set of resources of the type (search interaction)\">Search</b></th><th><b title=\"PUT a new resource version (update interaction)\">Update</b></th><th><b title=\"POST a new resource (create interaction)\">Create</b></th></tr></table></div>"
  },
  "url" : "http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-destination-server",
  "version" : "1.0.0",
  "name" : "ExchangeRoutingDestinationServerCapabilityStatement",
  "title" : "Exchange Routing Destination Server Capability Statement",
  "status" : "active",
  "experimental" : false,
  "date" : "2022-05-17T00:00:00-05:00",
  "publisher" : "HL7 International - FHIR Infrastructure",
  "contact" : [
    {
      "name" : "HL7 International - FHIR Infrastructure",
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    },
    {
      "name" : "Frank McKinney",
      "telecom" : [
        {
          "system" : "email",
          "value" : "frank.mckinney@pocp.com"
        }
      ]
    }
  ],
  "description" : "This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "urn:iso:std:iso:3166",
          "code" : "US",
          "display" : "United States of America"
        }
      ]
    }
  ],
  "kind" : "requirements",
  "fhirVersion" : "4.0.1",
  "format" : [
    "xml",
    "json"
  ],
  "patchFormat" : [
    "application/json-patch+json"
  ],
  "implementationGuide" : [
    "http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing"
  ],
  "rest" : [
    {
      "mode" : "server",
      "documentation" : "When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the destination server **SHALL** populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. \nWhen participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server **SHOULD**: 1. Support the XML source format.",
      "security" : {
        "description" : "1. Communication security implemented by the server SHALL conform with the guidelines stated in [FHIR Security](https://www.hl7.org/fhir/security.html) for all exchanges covered in this IG. \n1. The server MAY implement the [HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide](http://hl7.org/fhir/us/udap-security/2021Sep). 1. For general security considerations refer to [FHIR Security and Privacy Considerations](https://www.hl7.org/fhir/secpriv-module.html)."
      }
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.